Nice. My thoughts:

1. The binary itself is - as expected - big, but still smaller than I expected.
2. Testing this executable using existing tests is partially possible - there are "example specs" that test how bashly executable behaves (contrary to the Ruby unit tests) - but still, it would require some tweaking.
3. I for one am not interested in maintaining a packaging solution, unless it is dead simple and cross platform. The maintainer of such a binary packaging solution would have to be able to build it for different platforms, and test it, and support it.
4. If this tebako route would mature, I would consider having it as a separate repository that uses GitHub Actions to build it.

For completeness - could you specify what are the steps/commands needed to build the binary?

1 - yeah at 34m its actually much smaller than i thought it would be
2 - good to know.
3/4 - yeah, I think it would be easy to setup a ci that clones from your repo and builds binaries accordingly to it

steps for compilation -

1. clone the repo
2. setup tebako locally / download/use the docker image
3. run tebako press -D --entry-point=bashly --root /wd -R 3.4.1 (assume source code at /wd)